Bundle org.nuxeo.runtime.stream
Documentation
-
README.md
nuxeo-runtime-stream
About
This module provides an integration of nuxeo-stream with Nuxeo. It adds 2 services:
- a Kafka configuration service: to register Kafka and Zookeeper access and consumer producer properties.
- a Stream service: to define LogManager configuration, initialize Log and start StreamProcessor.
Kafka Configurations
You can register one or multiple Kafka configurations using this Nuxeo extension point:
<?xml version="1.0"?> <component name="my.project.kafka.contrib"> <extension target="org.nuxeo.runtime.stream.kafka.service" point="kafkaConfig"> <kafkaConfig name="default" zkServers="localhost:2181" topicPrefix="nuxeo-"> <producer> <property name="bootstrap.servers">localhost:9092</property> </producer> <consumer> <property name="bootstrap.servers">localhost:9092</property> <property name="request.timeout.ms">65000</property> <property name="max.poll.interval.ms">60000</property> <property name="session.timeout.ms">20000</property> <property name="heartbeat.interval.ms">1000</property> <property name="max.poll.records">50</property> </consumer> </kafkaConfig> </extension> </component>
This Kafka configuration named
default
can be used in the Log configuration below.Make sure you have read the nuxeo-stream README to setup properly Kafka.
Stream Service
This service enable to define Log configurations and to register stream processors.
The Log configuration
There are 2 types of Log configurations:
- In-Memory: limited for single node: all producers and consumers must be on the same node. No persistence.
- Kafka: required for distributed producers and consumers.
You can define a Log configuration with the following Nuxeo extension point:
<?xml version="1.0"?> <component name="my.project.stream.log.contrib"> <extension target="org.nuxeo.runtime.stream.service" point="logConfig"> ... (see documentation) ... </extension> </component>
The default Log type is In-Memory.
Using Log from Nuxeo
The Nuxeo Stream service enables to get and share access to LogManager:
StreamService service = Framework.getService(StreamService.class); LogManager manager = service.getLogManager("custom"); // write a record to myStream, the log exists because it has been initialized by the service LogAppender<Record> appender = manager.getAppender("myStream"); appender.append(key, Record.of(key, value.getBytes())); // read try (LogTailer<Record> tailer = manager.createTailer("myGroup", "myStream")) { LogRecord<Record> logRecord = tailer.read(Duration.ofSeconds(1)); assertEquals(key, logRecord.message().key); } // don't close the manager, this is done by the service
Stream processing
It is possible to register stream processors, this way they are initialized and started with Nuxeo.
The extension point refer to a class that returns the topology of computations, the settings are configurable in the contribution. Also the retry policy can be set to a specific computation or for all using
default
as policy name, thedelay
between retries, exponentially backing off to themaxDelay
and multiplying successive delays by a 2 factor themaxRetries
sets the max number of retries to perform. IfcontinueOnFailure
is true then the computation will checkpoint the record in error and continue processing new record. The default policy when unspecified is no retry and abort on failure (continueOnFailure
is false).<?xml version="1.0"?> <component name="my.project.stream.stream.contrib"> <extension target="org.nuxeo.runtime.stream.service" point="streamProcessor"> <streamProcessor name="myStreamProcessor" logConfig="default" defaultConcurrency="4" defaultPartitions="12" class="org.nuxeo.runtime.stream.tests.MyStreamProcessor"> <stream name="output" partitions="1" /> <computation name="myComputation" concurrency="8" /> <policy name="myComputation" continueOnFailure="false" maxRetries="3" delay="500ms" maxDelay="10s" /> </streamProcessor> </extension> </component>
About Nuxeo
Nuxeo dramatically improves how content-based applications are built, managed and deployed, making customers more agile, innovative and successful. Nuxeo provides a next generation, enterprise ready platform for building traditional and cutting-edge content oriented applications. Combining a powerful application development environment with SaaS-based tools and a modular architecture, the Nuxeo Platform and Products provide clear business value to some of the most recognizable brands including Verizon, Electronic Arts, Sharp, FICO, the U.S. Navy, and Boeing. Nuxeo is headquartered in New York and Paris. More information is available at www.nuxeo.com.
Resolution Order
You can influence this order by adding "require" tags in the component declaration, to make sure it is resolved after another component. It will also impact the order in which contributions are registered on their target extension point (see "Registration Order" on contributions).
Components
- org.nuxeo.runtime.stream.kafka.service
- org.nuxeo.runtime.stream.service
- org.nuxeo.runtime.stream.service.managment.contrib
- org.nuxeo.runtime.avro
- org.nuxeo.runtime.codec.service
- org.nuxeo.runtime.avro.contrib
Maven Artifact
File | nuxeo-runtime-stream-2023.22.13.jar |
---|---|
Group Id | org.nuxeo.runtime |
Artifact Id | nuxeo-runtime-stream |
Version | 2023.22.13 |
Manifest
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven 3.9.6
Built-By: root
Build-Jdk: 17.0.12
Bundle-ManifestVersion: 1
Bundle-Version: 2023.22.13-t20241121-011222
Bundle-Name: Nuxeo Runtime Stream
Bundle-SymbolicName: org.nuxeo.runtime.stream;singleton:=true
Bundle-Vendor: Nuxeo
Nuxeo-Component: OSGI-INF/kafka-config-service.xml,OSGI-INF/stream-servi
ce.xml,OSGI-INF/stream-management-contrib.xml,OSGI-INF/avro-service.xml
,OSGI-INF/codec-service.xml,OSGI-INF/avro-contrib.xml
Exports
- Json Export Default Json serialization
- Json Graph Json dependency graph
- Json Contribution Stats Json statistics for contributions
- CSV Contribution Stats CSV statistics for contributions
Charts
-
Raw Data: Json Contribution Stats